docs: update docs - #82

Summary

Update Docs

Type of change

• Bug fix
• New feature / capability
• New module
• Refactoring (no behavior change)
• Breaking change
• Documentation / tooling / CI only

Test plan

• mvn verify passes locally
• Live tests pass against the real Fanar API (if applicable, with FANAR_API_KEY set)
• GraalVM --self-test passes (if the SDK's reflective surface changed)

Reviewer checklist

• Public API changes are intentional, documented in javadoc, and an ADR was added/updated if the design changed
• Which *IntegrationTest proves the behaviour this PR claims? (100 % JaCoCo on a unit is not proof of wiring — see CONTRIBUTING "Testing")
• Breaking changes carry @Deprecated(since, forRemoval = true) and a migration path in the PR description
• BOM updated if modules were added or removed
• No third-party types leak into qa.fanar.core public API
• If a non-obvious project decision was made, capture it in memory/ so future contributors find it